github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-07-16 07:04:23 -05:00
Code Issues 3.0k Packages Projects Releases 58 Wiki Activity

[GH-ISSUE #6087] [Feature] Custom Budget Month Start Day #9539

New Issue
Closed
opened 2026-04-10 19:49:46 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-04-10 19:49:46 -05:00
Owner
Copy Link

Originally created by @WeebNetsu on GitHub (Nov 8, 2025).
Original GitHub issue: https://github.com/actualbudget/actual/issues/6087

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?

Currently when I get paid on the 25th of the month I would like to set my budget to be calculated for the next month, so if I get paid on the 25th of July and pay my Netflix subscription on the 28th of July, it should be counted towards the August budget, otherwise it causes confusion on most of the budgeted amount going off in the end of the month instead of near the start of the budgeting period

Describe your ideal solution to this problem

My current solution is to simply mark the payments as paid on the 1st of the next month, the ideal solution would be to have an optional setting that will count anything after a specified day of the month (ie. 25th) as part of the next months budget instead of the current month, this will keep the dates on my banking app the same but keep my budgets simple to understand an plan with

Teaching and learning

Simply put it under settings, maybe next to First day of the week field as "First day of budgeting period", with a description like: "If selected, then all new income/expenses items added from the x selected date of this month to the x selected date of next month will be considered the budget for the next month (so 25th-31st July will be considered as part of August)"

Originally created by @WeebNetsu on GitHub (Nov 8, 2025). Original GitHub issue: https://github.com/actualbudget/actual/issues/6087 ### 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? Currently when I get paid on the 25th of the month I would like to set my budget to be calculated for the next month, so if I get paid on the 25th of July and pay my Netflix subscription on the 28th of July, it should be counted towards the August budget, otherwise it causes confusion on most of the budgeted amount going off in the end of the month instead of near the start of the budgeting period ### Describe your ideal solution to this problem My current solution is to simply mark the payments as paid on the 1st of the next month, the ideal solution would be to have an optional setting that will count anything after a specified day of the month (ie. 25th) as part of the next months budget instead of the current month, this will keep the dates on my banking app the same but keep my budgets simple to understand an plan with ### Teaching and learning Simply put it under settings, maybe next to First day of the week field as "First day of budgeting period", with a description like: "If selected, then all new income/expenses items added from the x selected date of this month to the x selected date of next month will be considered the budget for the next month (so 25th-31st July will be considered as part of August)"
GiteaMirror added the feature label 2026-04-10 19:49:46 -05:00
GiteaMirror commented 2026-04-10 19:49:47 -05:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Nov 8, 2025):

Duplicate of #975. The standard practice for this is to hold your income to the next month so you are using the paycheck from the 25th to cover all of August not most of August and some of July.

<!-- gh-comment-id:3506542035 --> @youngcw commented on GitHub (Nov 8, 2025): Duplicate of #975. The standard practice for this is to hold your income to the next month so you are using the paycheck from the 25th to cover all of August not most of August and some of July.
GiteaMirror commented 2026-04-10 19:49:47 -05:00
Author
Owner
Copy Link

@jakub-sekula commented on GitHub (Nov 17, 2025):

Duplicate of #975. The standard practice for this is to hold your income to the next month so you are using the paycheck from the 25th to cover all of August not most of August and some of July.

This doesn't really solve the issue though right? It's forcing the user to work as the app wants it, rather than making the app work for the user. I think this is a common enough scenario where it would be good to have an explicit option on the app to set a custom date range for each budget period. This would also make it easier to account for shorter months or months where payday is brought forward by a week (common around Christmas time) and therefore a budget suddenly needs to stretch for 5 weeks instead of 4.

<!-- gh-comment-id:3543567990 --> @jakub-sekula commented on GitHub (Nov 17, 2025): > Duplicate of [#975](https://github.com/actualbudget/actual/issues/975). The standard practice for this is to hold your income to the next month so you are using the paycheck from the 25th to cover all of August not most of August and some of July. This doesn't really solve the issue though right? It's forcing the user to work as the app wants it, rather than making the app work for the user. I think this is a common enough scenario where it would be good to have an explicit option on the app to set a custom date range for each budget period. This would also make it easier to account for shorter months or months where payday is brought forward by a week (common around Christmas time) and therefore a budget suddenly needs to stretch for 5 weeks instead of 4.
GiteaMirror commented 2026-04-10 19:49:48 -05:00
Author
Owner
Copy Link

@code-with-jov commented on GitHub (Nov 21, 2025):

Hi @jakub-sekula

I'm working on something similar here

https://github.com/actualbudget/actual/issues/5849

But it does not allow the change for each individual budget period. There is one configuration in the settings that applies for all budget periods. If you don't mind taking a look at the preview and sharing some feedback that would be much appreciated.

https://deploy-preview-5730.demo.actualbudget.org/

<!-- gh-comment-id:3563497936 --> @code-with-jov commented on GitHub (Nov 21, 2025): Hi @jakub-sekula I'm working on something similar here https://github.com/actualbudget/actual/issues/5849 But it does not allow the change for each individual budget period. There is one configuration in the settings that applies for all budget periods. If you don't mind taking a look at the preview and sharing some feedback that would be much appreciated. https://deploy-preview-5730.demo.actualbudget.org/
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
tech-support
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label feature
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#9539
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?