github-actions[bot]
commented
1 month ago :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 👍!
Verified feature request does not already exist?
đź’»
Pitch: what problem are you trying to solve?
When budgeting based on a non-standard pay cycle (e.g., salary received on the 20th of the month), funds allocated from a late-month paycheck may be intended to cover expenses into the next month. However, because budgeting in ActualBudget is structured by calendar months, it currently considers these allocations as "fully funded" for the current month, leading to an "underfunded" status for the next month. This can cause confusion and create a misleading view of the financial situation.
Describe your ideal solution to this problem
Add an option in the budget settings to include future-dated income transactions in budget calculations. This way, the budget will account for income already allocated from the previous month, making it possible to accurately budget across pay periods instead of just calendar months. With this feature, users can see if they are underfunded or overfunded for the entire pay cycle rather than just per month.
Teaching and learning
No response