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 #554] [Feature] Allow users to manually set "From last month" in available funds in budget #7166

New Issue
Closed
opened 2026-04-10 16:51:58 -05:00 by GiteaMirror · 6 comments
GiteaMirror commented 2026-04-10 16:51:58 -05:00
Owner
Copy Link

Originally created by @rich-howell on GitHub (Jan 22, 2023).
Original GitHub issue: https://github.com/actualbudget/actual/issues/554

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

Originally posted by siegfriedpammer May 29, 2022
I am trying to start to use actualbudget to get an overview of my financial situation. I have imported all transactions of all my bank accounts starting from January 2022 and categorized them so I can get an overview of my spending. However, I will only be able to do proper budgeting from May or June 2022. In order to get correct results I would like to be able to set the "From last month" field of May ignoring all the previous months.
I know that I could simply remove all transactions before May or June, but I do not want that, because it is helpful to see past transactions when creating a new budget.
How can I achieve this? Thanks!

Unfortunately I am not a web dev, so I won't be able to contribute. Thank you for your work!

Originally created by @rich-howell on GitHub (Jan 22, 2023). Original GitHub issue: https://github.com/actualbudget/actual/issues/554 ### Discussed in https://github.com/actualbudget/actual/discussions/192 <div type='discussions-op-text'> <sup>Originally posted by **siegfriedpammer** May 29, 2022</sup> I am trying to start to use actualbudget to get an overview of my financial situation. I have imported all transactions of all my bank accounts starting from January 2022 and categorized them so I can get an overview of my spending. However, I will only be able to do proper budgeting from May or June 2022. In order to get correct results I would like to be able to set the "From last month" field of May ignoring all the previous months. I know that I could simply remove all transactions before May or June, but I do not want that, because it is helpful to see past transactions when creating a new budget. How can I achieve this? Thanks! Unfortunately I am not a web dev, so I won't be able to contribute. Thank you for your work!</div>
GiteaMirror commented 2026-04-10 16:51:59 -05:00
Author
Owner
Copy Link

@rich-howell commented on GitHub (Jan 31, 2023):

Hey @siegfriedpammer

Can you ellaborate on what your trying to achive here?

Cheers
Rich

<!-- gh-comment-id:1410443648 --> @rich-howell commented on GitHub (Jan 31, 2023): Hey @siegfriedpammer Can you ellaborate on what your trying to achive here? Cheers Rich
GiteaMirror commented 2026-04-10 16:51:59 -05:00
Author
Owner
Copy Link

@matharman commented on GitHub (Feb 4, 2023):

I found this issue while searching for a solution to the same problem. Maybe my 2 cents will help, too.

To get started with Actual, I imported transaction history from my & my partner's banks dating back to July 2019. Because I have no budget or categories set for those transactions, the To Budget amount shows that I have way, way more than my current account balances available for budgeting From Last Month -- roughly 6x more than my total balance.
EDIT: the description above came from user error. See my comment below for details.

It seems like what Actual wants me to do is to set my starting balances on Day 1 and only add new transactions from that day onward.

What I (and I think the OP) would like is to be able to keep our historical transactions to be able to view trends like Cash Flow, but to instruct Actual that I am starting my budget on Feb 3, 2023 -- and my From Last Month should only reflect the account balances at that time.

Does that help clarify? @siegfriedpammer please do chime in if this description does not sound like what you had in mind, and I'll create a separate issue.

<!-- gh-comment-id:1416658146 --> @matharman commented on GitHub (Feb 4, 2023): I found this issue while searching for a solution to the same problem. Maybe my 2 cents will help, too. To get started with Actual, I imported transaction history from my & my partner's banks dating back to July 2019. ~~Because I have no budget or categories set for those transactions, the `To Budget` amount shows that I have way, way more than my current account balances available for budgeting `From Last Month` -- roughly 6x more than my total balance.~~ EDIT: the description above came from user error. See [my comment below](https://github.com/actualbudget/actual/issues/554#issuecomment-1416832646) for details. It seems like what Actual wants me to do is to set my starting balances on Day 1 and only add new transactions from that day onward. What I (and I think the OP) would like is to be able to keep our historical transactions to be able to view trends like Cash Flow, but to instruct Actual that I am starting my budget on Feb 3, 2023 -- and my `From Last Month` should only reflect the account balances at that time. Does that help clarify? @siegfriedpammer please do chime in if this description does not sound like what you had in mind, and I'll create a separate issue.
GiteaMirror commented 2026-04-10 16:52:00 -05:00
Author
Owner
Copy Link

@matharman commented on GitHub (Feb 4, 2023):

I've had a bit more time to experiment, and this bit:

To Budget amount shows that I have way, way more than my current account balances available

was user error; I set the Starting Balance to the beginning of my transaction history, and categorized all paychecks from those 4 years as Income, leading to a much larger than expected To Budget amount.

After my experimenting I also think the feature request is better summarized as: allow user to mark the Running Balance of an account on a particular date/transaction as the Starting Balance.

<!-- gh-comment-id:1416832646 --> @matharman commented on GitHub (Feb 4, 2023): I've had a bit more time to experiment, and this bit: > To Budget amount shows that I have way, way more than my current account balances available was user error; I set the Starting Balance to the beginning of my transaction history, and categorized all paychecks from those 4 years as Income, leading to a much larger than expected To Budget amount. After my experimenting I also think the feature request is better summarized as: allow user to mark the Running Balance of an account on a particular date/transaction as the Starting Balance.
GiteaMirror commented 2026-04-10 16:52:00 -05:00
Author
Owner
Copy Link

@j-f1 commented on GitHub (Feb 4, 2023):

After my experimenting I also think the feature request is better summarized as: allow user to mark the Running Balance of an account on a particular date/transaction as the Starting Balance.

What do you mean by this? “Starting Balance” is just another transaction in your account history. (the only special behavior is that we look for a payee named that and create one if it’s missing when adding a new account)

<!-- gh-comment-id:1416837953 --> @j-f1 commented on GitHub (Feb 4, 2023): > After my experimenting I also think the feature request is better summarized as: allow user to mark the Running Balance of an account on a particular date/transaction as the Starting Balance. What do you mean by this? “Starting Balance” is just another transaction in your account history. (the only special behavior is that we look for a payee named that and create one if it’s missing when adding a new account)
GiteaMirror commented 2026-04-10 16:52:00 -05:00
Author
Owner
Copy Link

@matharman commented on GitHub (Feb 4, 2023):

Sorry, maybe Starting Balance had nothing to do with it -- my transaction history isn't categorized so manipulating the Starting Balance category was the only way I could seem to get the To Budget view to change in an expected way.

It could be that I am just using Actual totally wrong, but what I'm trying to accomplish is to have my old account history stay uncategorized (it would be cumbersome to go through that 4yr history), but have To Budget value reflect my Running Balance from the day I imported the transactions. I will of course categorize new & future transactions, so that I can actually budget.

For now my work around is to categorize every "historical" transaction as Starting Balance, but this feels like an abuse of that category.

As the OP mentioned, it seems like the other option currently is to remove all my account history and just set the Starting Balance in one transaction, then only add future transactions.

It would be nice if instead I could tell Actual to start budgeting with the Running Balance on the date I imported the transactions, instead of having to categorize the full history.

My specific case looks like this (collapsed because it's not directly related to the discussion, but might help illustrate my problem).

With one account, I have the full transaction history from the time it was opened (2019-present). Since that history is quite long, I don't want to go through and categorize everything as it would be cumbersome; but I want to keep the balance history to look at Cash Flow trends.

Because I have the full history, I set the Starting Balance as a $0 transaction back in 2019. At this point, the To Budget view showed $0 -- probably because nothing is categorized, other than this single transaction.

Next I categorized all my past paychecks as Income to see if I could leave only the outflow uncategorized; but that made To Budget show all my income ever since 2019.

I suspect if I went through and categorized everything, it would work out to the current Running Balance like I wanted. Instead I just marked everything as Starting Balance, which caused To Budget showed the value I expected.

<!-- gh-comment-id:1416847416 --> @matharman commented on GitHub (Feb 4, 2023): Sorry, maybe Starting Balance had nothing to do with it -- my transaction history isn't categorized so manipulating the Starting Balance category was the only way I could seem to get the To Budget view to change in an expected way. It could be that I am just using Actual totally wrong, but what I'm trying to accomplish is to have my old account history stay uncategorized (it would be cumbersome to go through that 4yr history), but have To Budget value reflect my Running Balance from the day I imported the transactions. I will of course categorize new & future transactions, so that I can actually budget. For now my work around is to categorize every "historical" transaction as Starting Balance, but this feels like an abuse of that category. As the OP mentioned, it seems like the other option currently is to remove all my account history and just set the Starting Balance in one transaction, then only add future transactions. It would be nice if instead I could tell Actual to start budgeting with the Running Balance on the date I imported the transactions, instead of having to categorize the full history. <details> <summary> My specific case looks like this (collapsed because it's not directly related to the discussion, but might help illustrate my problem). </summary> With one account, I have the full transaction history from the time it was opened (2019-present). Since that history is quite long, I don't want to go through and categorize everything as it would be cumbersome; but I want to keep the balance history to look at Cash Flow trends. Because I have the full history, I set the Starting Balance as a $0 transaction back in 2019. At this point, the To Budget view showed $0 -- probably because nothing is categorized, other than this single transaction. Next I categorized all my past paychecks as Income to see if I could leave only the outflow uncategorized; but that made To Budget show all my income ever since 2019. I suspect if I went through and categorized everything, it would work out to the current Running Balance like I wanted. Instead I just marked everything as Starting Balance, which caused To Budget showed the value I expected. </details>
GiteaMirror commented 2026-04-10 16:52:01 -05:00
Author
Owner
Copy Link

@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 👍!

<!-- gh-comment-id:1530131681 --> @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 👍!
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#7166
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?