mirror of
https://github.com/actualbudget/actual.git
synced 2026-07-15 14:43:36 -05:00
[Feature] Allow users to manually set "From last month" in available funds in budget #226
Closed
opened 2026-02-28 18:53:14 -06:00 by GiteaMirror
·
6 comments
No Branch/Tag Specified
master
tabedzki/feat/replacing-month-picker-with-day-picker
enforce-append-only-migrations-ci
delay-initial-sync-until-loaded
jfdoming/mobile-app-build
cross-version-sync-compat
claude/error-codes-worker-boundary-26i5uu
jfdoming/api-tokens-part-1
jfdoming/api-tokens-part-2
jfdoming/api-tokens-part-3
jfdoming/mobile-app-updates
api-browser-custom-data-dir
claude/budget-version-migration-compat-151jlr
claude/worker-error-serialization-9iqtl7
claude/react-table-library-research-afx83z
claude/issue-8401-regression-test-9nw9l3
jfdoming/mobile-app-foundation-part-1
jfdoming/mobile-app-scaffold
release
ai-fix-cleanup-def-8290
claude/relaxed-shannon-jusywa
claude/fervent-keller-s6f2fq
claude/determined-feynman-st1y9z
claude/wizardly-einstein-vi2wce
claude/sweet-albattani-7nseio
feat/bank-sync-per-budget-file
claude/affectionate-cannon-y0kc82
claude/dependabot-findings-m9pgmb
claude/mac-app-ios-publish-zjs1lz
claude/vigilant-tesla-aiiyos
depot-migrate-secrets-1781296330308
claude/quirky-cerf-v5qck7
claude/animation-removal-alternative-2etfh1
claude/netlify-preview-comments-consolidate-9XPYa
osc/7391-error-boundaries-reports
claude/pensive-dijkstra-7DYui
claude/server-app-version-mismatch-HTCGv
claude/pr-8027-review-feedback-mELuO
claude/zealous-wozniak-e5pO0
claude/intelligent-heisenberg-BSHJq
claude/translation-download-refactor-jFRsO
claude/mobile-performance-ideas-G9PAO
claude/github-issue-7988-5A5ly
blacksmith-migration-ff70d2d
claude/great-mayer-KRvOk
claude/react-native-ios-compilation-fcJh5
claude/serene-goldberg-58xv0
claude/kind-euler-LVG3K
release-automation/edge-nightly
7710-bundle-migrations
claude/fix-docker-build-error-WMfed
claude/llm-compatible-release-notes-t20Nr
7710-tests-tdd
cursor/transaction-table-rewrite-f077
claude/plan-ci-secure-context-OtEe1
claude/fix-issue-7667-DPXi3
cursor/resolve-pr-7449-ee11
claude/fix-typescript-build-error-JPtZ5
copilot/add-repository-configs-to-packages
worktree-compressed-drifting-ritchie
claude/api-consumer-verification-kfz1K
pr-7454
claude/fix-issue-7410-LLLQ4
revert-7281-generate-icons
react-query-useSchedules
copilot/sub-pr-6140
package-upgrades
v26.7.0
v26.6.0
v26.5.2
v26.5.1
v26.5.0
v26.4.0
v26.3.0
v26.2.1
v26.2.0
v26.1.0
v25.12.0
v25.11.0
v25.10.0
v25.9.0
v25.8.0
v25.7.1
v25.7.0
v25.6.1
v25.6.0
v25.5.0
v25.4.0
v25.3.1
v25.3.0
v25.2.1
v25.2.0
v25.1.0
v24.12.0
v24.11.0
v24.10.1
v24.10.0
v24.9.0
v24.8.0
v24.7.0
v24.6.0
v24.5.0
v24.4.0
v24.3.0
v24.2.0
v24.1.0
v23.12.0
v23.11.0
v23.10.0
v23.9.0
v23.8.1
v23.8.0
v23.7.2
v23.7.1
v23.7.0
v23.6.0
v23.5.0
v23.4.2
v23.4.1
v23.4.0
v23.3.2
v23.3.0
v23.2.9
v23.2.5
v23.1.12
v22.12.9
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
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
Mirrored from GitHub Pull Request
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/actual#226
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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?
Originally created by @rich-howell on GitHub (Jan 22, 2023).
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!
@rich-howell commented on GitHub (Jan 31, 2023):
Hey @siegfriedpammer
Can you ellaborate on what your trying to achive here?
Cheers
Rich
@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, theTo Budgetamount shows that I have way, way more than my current account balances available for budgetingFrom 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 Monthshould 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.
@matharman commented on GitHub (Feb 4, 2023):
I've had a bit more time to experiment, and this bit:
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.
@j-f1 commented on GitHub (Feb 4, 2023):
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)
@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.
@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 👍!