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 #1381] Feature request: Schedule Income for the NEXT MONTH #14758

New Issue
Closed
opened 2026-04-14 17:33:13 -05:00 by GiteaMirror · 10 comments
GiteaMirror commented 2026-04-14 17:33:13 -05:00
Owner
Copy Link

Originally created by @faspina on GitHub (Jul 21, 2023).
Original GitHub issue: https://github.com/actualbudget/actual/issues/1381

I get paid on the last day of the month , sometimes it hits on the 28ht or 29th. I want to designate this money to be utilized int he next month budget rather than the current month.
I would like to see a INCOME: NEXT MONTH category that push a July 28 paycheck to income for August

YNAB was able to do this and it works very well

Originally created by @faspina on GitHub (Jul 21, 2023). Original GitHub issue: https://github.com/actualbudget/actual/issues/1381 I get paid on the last day of the month , sometimes it hits on the 28ht or 29th. I want to designate this money to be utilized int he next month budget rather than the current month. I would like to see a INCOME: NEXT MONTH category that push a July 28 paycheck to income for August YNAB was able to do this and it works very well
GiteaMirror commented 2026-04-14 17:33:14 -05:00
Author
Owner
Copy Link

@kyrias commented on GitHub (Jul 21, 2023):

What would the advantage be over using the "hold for next month" functionality?

<!-- gh-comment-id:1646129803 --> @kyrias commented on GitHub (Jul 21, 2023): What would the advantage be over using the "hold for next month" functionality?
GiteaMirror commented 2026-04-14 17:33:14 -05:00
Author
Owner
Copy Link

@faspina commented on GitHub (Jul 21, 2023):

If my paycheck clears on Jun 29th or Jun 30th , I won't use that money in June. It will be budgeted for July expenses. As a result July budget show actual income allocated for July

<!-- gh-comment-id:1646129810 --> @faspina commented on GitHub (Jul 21, 2023): If my paycheck clears on Jun 29th or Jun 30th , I won't use that money in June. It will be budgeted for July expenses. As a result July budget show actual income allocated for July
GiteaMirror commented 2026-04-14 17:33:15 -05:00
Author
Owner
Copy Link

@kyrias commented on GitHub (Jul 21, 2023):

If you use the "hold for next month" feature then while it'll show up in the income category in June, because that's when you actually received it, it won't be available for budget purposes until July.

<!-- gh-comment-id:1646129815 --> @kyrias commented on GitHub (Jul 21, 2023): If you use the "hold for next month" feature then while it'll show up in the income category in June, because that's when you actually received it, it won't be available for budget purposes until July.
GiteaMirror commented 2026-04-14 17:33:15 -05:00
Author
Owner
Copy Link

@Kidglove57 commented on GitHub (Jul 21, 2023):

@faspina
Here is screenshot showing you the button, illustrative only I had no more income to send to next month!

image

<!-- gh-comment-id:1646202926 --> @Kidglove57 commented on GitHub (Jul 21, 2023): @faspina Here is screenshot showing you the button, illustrative only I had no more income to send to next month! ![image](https://github.com/actualbudget/actual/assets/93882449/27f2fc9a-fdf1-406c-a1ed-32601906cdb0)
GiteaMirror commented 2026-04-14 17:33:15 -05:00
Author
Owner
Copy Link

@Kidglove57 commented on GitHub (Jul 21, 2023):

And here is the current documentation that included this feature (scroll down a bit):

https://actualbudget.org/docs/budgeting/

Very similar to YNAB 4 but more flexible

<!-- gh-comment-id:1646206865 --> @Kidglove57 commented on GitHub (Jul 21, 2023): And here is the current documentation that included this feature (scroll down a bit): https://actualbudget.org/docs/budgeting/ Very similar to YNAB 4 but more flexible
GiteaMirror commented 2026-04-14 17:33:16 -05:00
Author
Owner
Copy Link

@faspina commented on GitHub (Jul 21, 2023):

I got it working, thanks

<!-- gh-comment-id:1646208323 --> @faspina commented on GitHub (Jul 21, 2023): I got it working, thanks
GiteaMirror commented 2026-04-14 17:33:16 -05:00
Author
Owner
Copy Link

@darthlite commented on GitHub (Dec 8, 2023):

Related question I guess: Aside from manually inputting a new date, is there a way to get this month's income to show up as next month's income in reports and such?

If I receive income towards the end of November, but use it to budget for December, I would like to compare it to December's expenses.

Problem with changing the date is it messes up the transactions and account syncing.

<!-- gh-comment-id:1847439117 --> @darthlite commented on GitHub (Dec 8, 2023): Related question I guess: Aside from manually inputting a new date, is there a way to get this month's income to show up as next month's income in reports and such? If I receive income towards the end of November, but use it to budget for December, I would like to compare it to December's expenses. Problem with changing the date is it messes up the transactions and account syncing.
GiteaMirror commented 2026-04-14 17:33:17 -05:00
Author
Owner
Copy Link

@faspina commented on GitHub (Dec 8, 2023):

I don't like the HOLD for next month option because I do have etra money after budget that I want to alocate to envelops but this amount is a paycheck. I like the idea of doing this at the transaction level , a tag that says use this next month maybe. With a stead y pay check every 30 of the month it would just be easier to do it this way

<!-- gh-comment-id:1847496195 --> @faspina commented on GitHub (Dec 8, 2023): I don't like the HOLD for next month option because I do have etra money after budget that I want to alocate to envelops but this amount is a paycheck. I like the idea of doing this at the transaction level , a tag that says use this next month maybe. With a stead y pay check every 30 of the month it would just be easier to do it this way
GiteaMirror commented 2026-04-14 17:33:18 -05:00
Author
Owner
Copy Link

@shawalli commented on GitHub (Aug 15, 2024):

I really like the way YNAB does it, where you can either assign a transaction to "Income: this month" or "Income: next month". The reason I like this approach better than the "hold" method is I don't need to do any math or special tricks to figure out how much money it available in the current or next month to budget. Additionally, when looking backward, you can easily see which income transactions are siloed into which months, rather than a floating level of money.

Having used AB for about 6 months now, it is one of the two features I still long for, because it makes the income management process dead-simple (at least as a user; I make no claims as to how it would be implemented behind the scenes).

<!-- gh-comment-id:2290148953 --> @shawalli commented on GitHub (Aug 15, 2024): I really like the way YNAB does it, where you can either assign a transaction to "Income: this month" or "Income: next month". The reason I like this approach better than the "hold" method is I don't need to do any math or special tricks to figure out how much money it available in the current or next month to budget. Additionally, when looking backward, you can easily see which income transactions are siloed into which months, rather than a floating level of money. Having used AB for about 6 months now, it is one of the two features I still long for, because it makes the income management process dead-simple (at least as a user; I make no claims as to how it would be implemented behind the scenes).
GiteaMirror commented 2026-04-14 17:33:18 -05:00
Author
Owner
Copy Link

@arwandar commented on GitHub (Oct 28, 2024):

What about a 2 incomes household? I'm get paid on the 29th, but my husband is paid the 2nd. So I can't use hold for next month as it won't solve the problem. I would like as @faspina to have the setting at a transaction level.

<!-- gh-comment-id:2441236163 --> @arwandar commented on GitHub (Oct 28, 2024): What about a 2 incomes household? I'm get paid on the 29th, but my husband is paid the 2nd. So I can't use hold for next month as it won't solve the problem. I would like as @faspina to have the setting at a transaction level.
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
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#14758
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?