[Feature] Manually categorise transactions as Upcoming #186

Closed
opened 2026-02-28 18:51:35 -06:00 by GiteaMirror · 6 comments
Owner

Originally created by @rich-howell on GitHub (Jan 22, 2023).

Discussed in https://github.com/actualbudget/actual/discussions/253

Originally posted by isiko September 26, 2022
I don't see a good way to add one-time Transactions that haven't happened yet. If the Transactions are part of a schedule, they are shown as "Upcoming", it would be nice to be able to flag manually added transactions like that too.

Originally created by @rich-howell on GitHub (Jan 22, 2023). ### Discussed in https://github.com/actualbudget/actual/discussions/253 <div type='discussions-op-text'> <sup>Originally posted by **isiko** September 26, 2022</sup> I don't see a good way to add one-time Transactions that haven't happened yet. If the Transactions are part of a schedule, they are shown as "Upcoming", it would be nice to be able to flag manually added transactions like that too.</div>
Author
Owner

@joaociocca commented on GitHub (Mar 31, 2023):

second that! I don't know how to help on coding, but I can help on testing... since I suffer from this terribly =p I didn't even knew there was a "Upcoming" feature, until I saw this one today... and it's really weird that things with a date AFTER the new "Upcoming" transaction show as before it. Maybe make it so all transactions beyond current day show up as Upcoming?
image

@joaociocca commented on GitHub (Mar 31, 2023): second that! I don't know how to help on coding, but I can help on testing... since I suffer from this terribly =p I didn't even knew there was a "Upcoming" feature, until I saw this one today... and it's really weird that things with a date AFTER the new "Upcoming" transaction show as before it. Maybe make it so all transactions beyond current day show up as Upcoming? ![image](https://user-images.githubusercontent.com/6473725/229247586-3317c9f2-3695-4863-93e7-0086ffdca3f5.png)
Author
Owner

@Kidglove57 commented on GitHub (Apr 1, 2023):

May also link in with issue 550 - display running balance against upcoming transactions (as a forecast feature?)

@Kidglove57 commented on GitHub (Apr 1, 2023): May also link in with issue 550 - display running balance against upcoming transactions (as a forecast feature?)
Author
Owner

@github-actions[bot] commented on GitHub (May 1, 2023):

Thanks for sharing your idea!

This repository is now using lodash style issue management for enhancements. This means enhancement issues will now be closed instead of leaving them open. 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 👍!

@github-actions[bot] commented on GitHub (May 1, 2023): :sparkles: Thanks for sharing your idea! :sparkles: This repository is now using lodash style issue management for enhancements. This means enhancement issues will now be closed instead of leaving them open. 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 👍!
Author
Owner

@atgrey24 commented on GitHub (Jul 16, 2024):

Reviving this old request. I don't like the current behavior where future transactions post immediately and are available to be budgeted, and creating schedules for one time transactions is clunky. I would go so far as saying future transactions should be treated as scheduled/upcoming by default, but understand if that's a step too far.

@atgrey24 commented on GitHub (Jul 16, 2024): Reviving this old request. I don't like the current behavior where future transactions post immediately and are available to be budgeted, and creating schedules for one time transactions is clunky. I would go so far as saying future transactions should be treated as scheduled/upcoming by default, but understand if that's a step too far.
Author
Owner

@BreaklessMonkey commented on GitHub (Sep 5, 2025):

I would also like future transactions entered manually, not to be taken into account for the balance of the accounts
This issue is marked as closed but I did not find a way to change this in Actual

@BreaklessMonkey commented on GitHub (Sep 5, 2025): I would also like future transactions entered manually, not to be taken into account for the balance of the accounts This issue is marked as closed but I did not find a way to change this in Actual
Author
Owner

@atgrey24 commented on GitHub (Sep 23, 2025):

I would also like future transactions entered manually, not to be taken into account for the balance of the accounts This issue is marked as closed but I did not find a way to change this in Actual

@BreaklessMonkey You can use schedules to enter future transactions without affecting current balances. It's a bit clunky when all you want to do is enter a one-off transaction, but it does work.

@atgrey24 commented on GitHub (Sep 23, 2025): > I would also like future transactions entered manually, not to be taken into account for the balance of the accounts This issue is marked as closed but I did not find a way to change this in Actual @BreaklessMonkey You can use schedules to enter future transactions without affecting current balances. It's a bit clunky when all you want to do is enter a one-off transaction, but it does work.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#186