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

[GH-ISSUE #5849] [Feature] Pay Periods #9455

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

Originally created by @code-with-jov on GitHub (Oct 4, 2025).
Original GitHub issue: https://github.com/actualbudget/actual/issues/5849

Verified feature request does not already exist?

  • #975 seems similar

💻

  • Would you like to implement this feature?

Pitch: what problem are you trying to solve?

The biggest challenge with any budget is knowing you’ll have the right amount of money at the right time. Actual Budget’s envelop method does a great job of tracking this by encouraging you to plan only with the money you currently have.

A Pay Period view would allow for planning in income driven slices. Instead of an arbitrary month, a user could select whether they get paid weekly, bi-weekly, etc. and there budget view would be broken down in that time range (e.g Aug 29th - Sep 12th). This allows for planning with numbers proportional to and with the time reference of your income.

Additionally, a Pay Period view solves the Tracking Budget’s biggest issue. Since the time slices are income driven, you can be more confident you’ll have the right amount of money when you need it.

Describe your ideal solution to this problem

This approach emphasizes backwards compatibility by adding additional "months" to YYYYMM. 1 - 12 remain Calendar Months, while 13 - 99 are leveraged for Pay Periods. It is calculation heavy, as it uses the Frequency and Start Date configurations set on the settings page (only visible after enabling the experimental feature) to derive date ranges. A "Show Pay Periods" checkbox is displayed at the top of the budget page - allowing users to quickly toggle between Month and Pay Period views.

I did already start this: https://github.com/actualbudget/actual/pull/5730 but re-read the contributing docs and realized I missed creating an issue. Still very much a work in progress, a lot of clean up left to do!

Teaching and learning

Add docs to Experimental features Section on how to enable and how the date ranges are calculated.

Originally created by @code-with-jov on GitHub (Oct 4, 2025). Original GitHub issue: https://github.com/actualbudget/actual/issues/5849 ### Verified feature request does not already exist? - [ ] #975 seems similar ### 💻 - [x] Would you like to implement this feature? ### Pitch: what problem are you trying to solve? The biggest challenge with any budget is knowing you’ll have the right amount of money at the right time. Actual Budget’s envelop method does a great job of tracking this by encouraging you to plan only with the money you currently have. A Pay Period view would allow for planning in income driven slices. Instead of an arbitrary month, a user could select whether they get paid weekly, bi-weekly, etc. and there budget view would be broken down in that time range (e.g Aug 29th - Sep 12th). This allows for planning with numbers proportional to and with the time reference of your income. Additionally, a Pay Period view solves the Tracking Budget’s biggest issue. Since the time slices are income driven, you can be more confident you’ll have the right amount of money when you need it. ### Describe your ideal solution to this problem This approach emphasizes backwards compatibility by adding additional "months" to YYYYMM. 1 - 12 remain Calendar Months, while 13 - 99 are leveraged for Pay Periods. It is calculation heavy, as it uses the Frequency and Start Date configurations set on the settings page (only visible after enabling the experimental feature) to derive date ranges. A "Show Pay Periods" checkbox is displayed at the top of the budget page - allowing users to quickly toggle between Month and Pay Period views. I did already start this: https://github.com/actualbudget/actual/pull/5730 but re-read the contributing docs and realized I missed creating an issue. Still very much a work in progress, a lot of clean up left to do! ### Teaching and learning Add docs to Experimental features Section on how to enable and how the date ranges are calculated.
GiteaMirror added the featureneeds votes labels 2026-04-10 19:43:49 -05:00
GiteaMirror commented 2026-04-10 19:43:53 -05:00
Author
Owner
Copy Link

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

<!-- gh-comment-id:3367899474 --> @github-actions[bot] commented on GitHub (Oct 4, 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 -->
GiteaMirror commented 2026-04-10 19:43:54 -05:00
Author
Owner
Copy Link

@humrochagf commented on GitHub (Oct 6, 2025):

This exactly what I was looking for, I moved from google sheets 4 months ago and it was a great usability upgrade, but It came with the downside that at home we started to feel less on the control of our budged in comparison to the sheets because there we had the budget matching exactly our bi-weekly payments and bills that we also split to match our payment.

Even to automate it became a bit clumsly since now we have to calculate the porportion of bi-weekly regarding the month to alocate in the budget and do it 2 or 3 times a month acoording with how many payments lands on that month.

<!-- gh-comment-id:3374304674 --> @humrochagf commented on GitHub (Oct 6, 2025): This exactly what I was looking for, I moved from google sheets 4 months ago and it was a great usability upgrade, but It came with the downside that at home we started to feel less on the control of our budged in comparison to the sheets because there we had the budget matching exactly our bi-weekly payments and bills that we also split to match our payment. Even to automate it became a bit clumsly since now we have to calculate the porportion of bi-weekly regarding the month to alocate in the budget and do it 2 or 3 times a month acoording with how many payments lands on that month.
GiteaMirror commented 2026-04-10 19:43:55 -05:00
Author
Owner
Copy Link

@code-with-jov commented on GitHub (Oct 6, 2025):

Absolutely! I'm right there with you.

Progress is going pretty well if you want to try it out - I'm definitely looking for feedback:

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

I do still need to get it working on mobile and clean the code up.

<!-- gh-comment-id:3374623660 --> @code-with-jov commented on GitHub (Oct 6, 2025): Absolutely! I'm right there with you. Progress is going pretty well if you want to try it out - I'm definitely looking for feedback: https://deploy-preview-5730.demo.actualbudget.org/ I do still need to get it working on mobile and clean the code up.
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#9455
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?