github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-06 07:01:45 -05:00
Code Issues 1.5k Packages Projects Releases 54 Wiki Activity

[GH-ISSUE #2377] [Bug]: "To Budget" should take into consideration transactions with no category #7880

New Issue
Closed
opened 2026-04-10 17:59:50 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-04-10 17:59:50 -05:00
Owner
Copy Link

Originally created by @tavlima on GitHub (Feb 19, 2024).
Original GitHub issue: https://github.com/actualbudget/actual/issues/2377

Verified issue does not already exist?

  • I have searched and found no existing issue

Is this related to GoCardless, Simplefin or another bank-sync provider?

  • I have checked my server logs and could not see any errors there
  • I will be attaching my server logs to this issue
  • I will be attaching my client-side (browser) logs to this issue
  • I understand that this issue will be automatically closed if insufficient information is provided

What happened?

I just imported 6 months worth of transactions and didn't have time to go and classify all of them, but coming from nYNAB, I thought I could rely on the "To Budget" for current/future months, still... Except that I can't.

IMHO, the current behavior is misleading, as I definitely don't have 900 available for March.

The transactions

image

The budget

image

nYNAB transactions

image

nYNAB budget, for reference

image

image

What error did you receive?

No response

Where are you hosting Actual?

None

What browsers are you seeing the problem on?

No response

Operating System

None

Originally created by @tavlima on GitHub (Feb 19, 2024). Original GitHub issue: https://github.com/actualbudget/actual/issues/2377 ### Verified issue does not already exist? - [X] I have searched and found no existing issue ### Is this related to GoCardless, Simplefin or another bank-sync provider? - [ ] I have checked my server logs and could not see any errors there - [ ] I will be attaching my server logs to this issue - [ ] I will be attaching my client-side (browser) logs to this issue - [ ] I understand that this issue will be automatically closed if insufficient information is provided ### What happened? I just imported 6 months worth of transactions and didn't have time to go and classify all of them, but coming from nYNAB, I thought I could rely on the "To Budget" for current/future months, still... Except that I can't. IMHO, the current behavior is misleading, as I definitely don't have 900 available for March. --- > The transactions <img width="1724" alt="image" src="https://github.com/actualbudget/actual/assets/1283363/bbeef072-4f32-4f5f-9960-e4466b4fdb8c"> --- > The budget <img width="1725" alt="image" src="https://github.com/actualbudget/actual/assets/1283363/9358f1c4-90eb-4172-9f4a-ee5ec40b60b6"> --- > nYNAB transactions ![image](https://github.com/actualbudget/actual/assets/1283363/ec091036-9e67-4c50-9954-082f442fade5) --- > nYNAB budget, for reference ![image](https://github.com/actualbudget/actual/assets/1283363/0a7dd027-3dd4-456c-9f8a-3b2948438ada) ![image](https://github.com/actualbudget/actual/assets/1283363/3d4580d3-43a8-48a9-baac-a5e21f3b82b1) ### What error did you receive? _No response_ ### Where are you hosting Actual? None ### What browsers are you seeing the problem on? _No response_ ### Operating System None
GiteaMirror added the bug label 2026-04-10 17:59:50 -05:00
GiteaMirror commented 2026-04-10 17:59:52 -05:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Feb 19, 2024):

There is a feature request for this #1794. Closing the issue since its not really a bug, but its true that it can be confusing.

<!-- gh-comment-id:1953205397 --> @youngcw commented on GitHub (Feb 19, 2024): There is a feature request for this #1794. Closing the issue since its not really a bug, but its true that it can be confusing.
GiteaMirror commented 2026-04-10 17:59:52 -05:00
Author
Owner
Copy Link

@tavlima commented on GitHub (Feb 19, 2024):

I see. IMHO it is not just confusing: it makes the whole budget useless, unless you have all of those transactions categorized. In fact, this is the second bug report about the same thing, so I'm afraid we will have to disagree on how to classify this. If this is not a bug, then I guess it is "by design", which doesn't make much sense to me.

<!-- gh-comment-id:1953211645 --> @tavlima commented on GitHub (Feb 19, 2024): I see. IMHO it is not just confusing: it makes the whole budget useless, unless you have all of those transactions categorized. In fact, this is the second bug report about the same thing, so I'm afraid we will have to disagree on how to classify this. If this is not a bug, then I guess it is "by design", which doesn't make much sense to me.
GiteaMirror commented 2026-04-10 17:59:53 -05:00
Author
Owner
Copy Link

@tavlima commented on GitHub (Feb 19, 2024):

Also, apologies for not search thoroughly before posting this.

<!-- gh-comment-id:1953213909 --> @tavlima commented on GitHub (Feb 19, 2024): Also, apologies for not search thoroughly before posting this.
GiteaMirror commented 2026-04-10 17:59:54 -05:00
Author
Owner
Copy Link

@Kidglove57 commented on GitHub (Feb 20, 2024):

I have four years of records in Actual so of course I can’t fully appreciate your situation. However, leaving aside any rights or wrongs as to the issue you raise, I would have approached it this way:

  1. Set an opening balance on each account at the beginning of the series of imported transactions.
  2. Check that my account balances after import are still correct
  3. Categorise all the imported transactions as either “Pre Actual Expenses” or “Pre Actual income”
  4. Start budgeting in Actual from the beginning of a new month using the account balances available
  5. In due course use the “hide category” facility for the “ Pre Actual” categories.
<!-- gh-comment-id:1954058406 --> @Kidglove57 commented on GitHub (Feb 20, 2024): I have four years of records in Actual so of course I can’t fully appreciate your situation. However, leaving aside any rights or wrongs as to the issue you raise, I would have approached it this way: 1) Set an opening balance on each account at the beginning of the series of imported transactions. 2) Check that my account balances after import are still correct 3) Categorise all the imported transactions as either “Pre Actual Expenses” or “Pre Actual income” 4) Start budgeting in Actual from the beginning of a new month using the account balances available 5) In due course use the “hide category” facility for the “ Pre Actual” categories.
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 bug
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#7880
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?