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

[GH-ISSUE #3517] [Feature] Request for Improved Handling of Future and Uncleared Transactions in Budget and Account Views #43107

New Issue
Closed
opened 2026-04-26 03:22:19 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-26 03:22:19 -05:00
Owner
Copy Link

Originally created by @jviegas6 on GitHub (Sep 27, 2024).
Original GitHub issue: https://github.com/actualbudget/actual/issues/3517

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?

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

Originally created by @jviegas6 on GitHub (Sep 27, 2024). Original GitHub issue: https://github.com/actualbudget/actual/issues/3517 ### 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? 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_
GiteaMirror added the needs votesfeature labels 2026-04-26 03:22:20 -05:00
GiteaMirror commented 2026-04-26 03:22:24 -05:00
Author
Owner
Copy Link

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

<!-- gh-comment-id:2379227445 --> @github-actions[bot] commented on GitHub (Sep 27, 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
tech-support
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#43107
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?