github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-06 15:12:35 -05:00
Code Issues 1.5k Packages Projects Releases 54 Wiki Activity

[Feature] Choose budget frequency #1727

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

Originally created by @ElDubsNZ on GitHub (Dec 30, 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?

Most budgeting apps are based around the American system of being paid monthly. But in many places, paycheques are weekly or even fortnightly (2-weekly for Americans).

For people paid monthly, this works great, they can plan ahead for their next paycheque, but for the rest of us, we have to awkwardly plan 2-4 "and a bit" paycheques in one budget period. It really diminishes the usefulness of the budget for me as a fortnightly paid person.

Describe your ideal solution to this problem

Allow us to choose our budget frequency by setting a start date and an end date that match our pay period. For example, my last pay day was 24 December, so I would pick 2024-12-24 to 2025-01-06. Actual would then set pay periods every 14 days.

I have no doubt this would be a major restructure of how budgets are coded and organised, but it would bring so much benefit to those of us who aren't paid monthly.

Switching between budgets might have to be impossible. Merging from smaller periods to larger periods is easy enough, just combine the periods, however splitting down, Actual would have no way to know which fortnight to put the budgeted amount into. So I suspect it'd be easier if there's just different budgeting databases for each frequency.

As for UI, instead of showing the month, it would show the period you've selected.

Teaching and learning

Depending on how it's built, this would be either something chosen when creating a new budget, or it's something you can change in the budget menu. You could recommend people set it based on their pay frequency.

Originally created by @ElDubsNZ on GitHub (Dec 30, 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? Most budgeting apps are based around the American system of being paid monthly. But in many places, paycheques are weekly or even fortnightly (2-weekly for Americans). For people paid monthly, this works great, they can plan ahead for their next paycheque, but for the rest of us, we have to awkwardly plan 2-4 "and a bit" paycheques in one budget period. It really diminishes the usefulness of the budget for me as a fortnightly paid person. ### Describe your ideal solution to this problem Allow us to choose our budget frequency by setting a start date and an end date that match our pay period. For example, my last pay day was 24 December, so I would pick 2024-12-24 to 2025-01-06. Actual would then set pay periods every 14 days. I have no doubt this would be a major restructure of how budgets are coded and organised, but it would bring so much benefit to those of us who aren't paid monthly. Switching between budgets might have to be impossible. Merging from smaller periods to larger periods is easy enough, just combine the periods, however splitting down, Actual would have no way to know which fortnight to put the budgeted amount into. So I suspect it'd be easier if there's just different budgeting databases for each frequency. As for UI, instead of showing the month, it would show the period you've selected. ### Teaching and learning Depending on how it's built, this would be either something chosen when creating a new budget, or it's something you can change in the budget menu. You could recommend people set it based on their pay frequency.
GiteaMirror added the featureneeds votes labels 2026-02-28 19:53:11 -06:00
GiteaMirror commented 2026-02-28 19:53:12 -06:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Dec 30, 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 (Dec 30, 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 👍! <!-- 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#1727
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?