[Feature] 'Schedules' support for flexible yearly recurrences #1260

New Issue

GiteaMirror · 2026-02-28T19:37:48-06:00

GiteaMirror commented

2026-02-28 19:37:48 -06:00

Originally created by @jesstokes on GitHub (Jul 22, 2024).

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 am retiring and will be required to pay quarterly taxes to the IRS as a US citizen. Self-employed individuals in the USA often also have to pay taxes quarterly. The IRS tax deadlines are not evenly-spaced quarters 3 months apart. Rather taxes are due for Q1 in April, Q2 in June, Q3 in September, and Q4 in January of the next year. This means that to budget for (usually equal) quarterly payments, the amount to set aside differs per month. I have yet to find any combination of schedules and templates that addresses this in a reliable/error-free manner.

The benefit of this feature is that with a single Schedule, the user can leverage goals/templates to ensure they are saving enough for quarterly taxes without having to manually calculate the amount per quarter OR use averages (which results in under/over saving). Solving this problem may also meet other needs when schedules are not evenly distributed over days/weeks/months/years.

Describe your ideal solution to this problem

Ideally, Schedules would enable the user to enter N custom intervals creating a pattern that can be replicated each period. It appears this is already a feature for "Days" where multiple days in a month can be indicated. My request is to extend this behavior to month/day combinations that can be repeated over years.

Teaching and learning

I would address this where tax-related Categories are mentioned, as this feature enables a single Schedule:Category relationship to be maintained for simplicity.

Originally created by @jesstokes on GitHub (Jul 22, 2024). ### 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 am retiring and will be required to pay quarterly taxes to the IRS as a US citizen. Self-employed individuals in the USA often also have to pay taxes quarterly. The [IRS tax deadlines](https://www.irs.gov/faqs/estimated-tax/individuals/individuals-2) are not evenly-spaced quarters 3 months apart. Rather taxes are due for Q1 in April, Q2 in June, Q3 in September, and Q4 in January of the next year. This means that to budget for (usually equal) **quarterly** payments, the amount to set aside differs per month. I have yet to find any combination of schedules and templates that addresses this in a reliable/error-free manner. The benefit of this feature is that with a single Schedule, the user can leverage goals/templates to ensure they are saving enough for quarterly taxes without having to manually calculate the amount per quarter OR use averages (which results in under/over saving). Solving this problem may also meet other needs when schedules are not evenly distributed over days/weeks/months/years. ### Describe your ideal solution to this problem Ideally, Schedules would enable the user to enter N custom intervals creating a pattern that can be replicated each period. It appears this is already a feature for "Days" where multiple days in a month can be indicated. My request is to extend this behavior to month/day combinations that can be repeated over years. ### Teaching and learning I would address this where tax-related Categories are mentioned, as this feature enables a single Schedule:Category relationship to be maintained for simplicity.

GiteaMirror added the needs votes feature labels 2026-02-28 19:37:48 -06:00

GiteaMirror closed this issue

2026-02-28 19:37:49 -06:00

GiteaMirror commented

2026-02-28 19:37:49 -06:00

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

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